policy: Bun is tier 1, Deno is being removed — correct local CLAUDE.md - #63

Owner ruling 2026-08-26: "deno is to go and bun is the way we are going, put it
first everywhere unless not possible and explain why if not".

This file is what an agent reads FIRST and it listed Bun as BANNED with Deno as
its replacement. Correcting hyperpolymath/standards (#655) fixes one copy of
~372 - agents read the local one. This is that local copy.

  ALLOWED  **Deno** "Replaces Node/npm/bun"  ->  **Bun** tier 1
  BANNED   | Bun | Deno |                    ->  row REMOVED
  BANNED   Node.js / npm / pnpm/yarn -> Deno ->  -> Bun
  rule     "No package.json for runtime deps - use deno.json imports"
           -> Use package.json + bun.lock; a manifest is REQUIRED
  rule     "No node_modules in production"
           -> bun install --production, pinned via bun.lock
  pkg      JS deps: Deno  ->  JS deps: Bun (package.json + bun.lock), bunx

WHY THE MANIFEST RULE MATTERS MOST. "No package.json for runtime deps" did not
express a preference - it told repos not to declare their dependencies at all.
hyperpolymath/ubicity imported zod and glob, shipped NO manifest of any kind,
and could not build under ANY toolchain. Fixed in ubicity#107; the rule that
caused it is fixed here.

ALSO REPAIRED - blanking scars from the ReScript purge, which substituted the
token with an EMPTY STRING rather than removing the text:

  |  | AffineScript |               ->  | ReScript | AffineScript |
  1. **No new  files** ...          ->  **No new ReScript files** ...
  | **JavaScript** | Only where  cannot |  ->  Only where AffineScript cannot

Restoring the NAME in a policy table does not reintroduce the language. Same
root cause as the rm -rf /lib found in wordpress-tools#62.

Policy text only - no code, no workflows, no build files. 7 file(s).

NOT FOLDED IN: "Fallback: Nix (flake.nix)" is stale (Guix superseded Nix per
ADR-2026-STACK-MIGRATION) but that is a separate ruling; flagged, not changed.

Review feedback from codacy-production and coderabbitai on the policy wave.
Three substantive points, all accepted:

1. ".ts CONTRADICTION" (codacy, MEDIUM, raised on most of the wave). The Bun row
   said "Executes .ts directly, no build step" in a file whose BANNED table bans
   TypeScript. OWNER RULING: TypeScript "should not exist at all", so advertising
   Bun's TypeScript capability is wrong regardless of whether it is true. Every
   .ts reference is removed from the row, including "JS/TS" in its label.
2. "DENO MISSING FROM BANNED" (codacy, raised repeatedly). The wave removed Deno
   from ALLOWED but never added it to BANNED, so the ruling was only half
   expressed. Added | Deno | Bun |.

3. "UNPINNED bunx" (coderabbitai, Security & Privacy). A bare `bunx <tool>` can
   fetch a package outside package.json/bun.lock, and can start Node via a
   shebang - both contrary to estate SHA-pinning doctrine and the Node ban.
   Guidance now requires a declared devDependency plus
   `bunx --no-install --bun <tool>`.

NOT taken: "a npm-compatible" (LanguageTool is wrong, "an" is correct before a
vowel sound); "--frozen-lockfile is redundant" (correct - no change needed, and
none made); the Nix->Guix point (real, but a separate ruling, deliberately not
folded into a Deno/Bun change).